Events - 1.44.0

 

To configure calorie information against menu items, you will need access to iOrder. For configuration, please click here

Impact

When a guest is making a pre-order via the Events Guest Portal, the calorie information will be displayed in three different scenarios. This information will be taken directly from iOrder and must be updated and maintained in that system.

1. When selecting a Menu Product

   • 

2. When selecting a Menu Portion

   • 

3. When selecting a Menu Choice

   • 

This feature impacts four key areas of Events, each of which is outlined below.

Booking Rules - add 'Place as enquiry' action

An Estate Admin can now add a new action to a booking rule called ‘Place as enquiry’. When triggered, any booking matching this rule will automatically save an event as an enquiry, not as a confirmed or provisional booking.

Enquiries originating from this booking rule will be placed as an enquiry, regardless of whether a time slot selected is configured to accept enquiries or not.

The enquiries Minimum Notice period, configured by an Events Estate Admin will be respected

Please find more details on how it functions in individual products below.

External API - apply 'Place as enquiry' action

When an event created via External API matches a ‘Place as enquiry’ booking rule, an error of ‘An enquiry should be created instead’ will be returned and an event won’t be saved. Instead, the createEnquiry request should be sent.

Additionally, similar to the Events schema, theEnquiry schema has been extended to include requirements property if any requirements exist.

The updated Events API specification can be found here

Online Widget - apply 'Place as enquiry' booking rule

Guests making bookings via Online Widget will be notified when their event is being placed as an enquiry, not as a confirmed booking.

Guests will not be able to place an enquiry within Enquiries Minimum Notice period, i.e. for today, as configured by an Estate Admin. They will be asked to change their selection.

Events & Tables Host apps - apply 'Place as enquiry' rule

An Events Host will be prompted to save an event as an enquiry, when selected details make it match a ‘Place as enquiry’ booking rule. However a Host has a choice of saving it either as an enquiry or as a booking.

As Tables Host app does not have a concept of enquiries, an event created in Tables will be saved as a provisional or confirmed booking and will never be saved as an enquiry, even if it matches a ‘Place as enquiry’ booking rule. Bookings created in Tables will still have other requirements originating from the matched booking rules,e.g. a deposit, if any.

Import - ignore 'Place as enquiry' action

Bookings imported from Reservations, even if matched to a ‘Place as enquiry’ booking rule, will be imported as bookings and not as enquiries. However, other requirements, e.g. a deposit or a pre-order, if any exists in a matched booking rule, will apply to imported bookings.

Prerequisites

• Events Capacity Management feature is enabled.

  • To enable this feature, please speak to your account manager.

• One or more Capacity Groups configured in Events Admin.

Configuration

1. Log in to Events as an Estate, Company, or Site Admin user.

2. Navigate to Capacity Management > Standard Day.

3. At the bottom of the timeslot creation tool, there is a new row of check boxes for capacity group selection
   
   

4. Complete the timeslot selection sentences and select any capacity groups you wish to bulk create timeslots for.
   
   

   NOTE: At least one capacity group must be selected.

5. On the timeslot configuration screen, you will now see which capacity groups you are creating timeslots for.
   
   

6. Select 'Create' and timeslots will be created for each capacity group you previously selected.

This process can be repeated multiple times for each capacity group

Creating timeslots for a capacity group that already has timeslots will override all previously created timeslots for the day and session combination